System and method for providing custom component compilation within a cloud-based content hub environment

ABSTRACT

Described herein are systems and methods for providing custom component compilation within a cloud-based content hub environment. In accordance with an embodiment, embodiments can allow developers to work with a variety of technologies and optimize a page or site for runtime performance, including in some instances the use of a custom (component) compiler, for use during compilation of a particular component of a website.

CLAIM OF PRIORITY AND CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. Provisionalapplication titled “SYSTEM AND METHOD FOR DYNAMIC SITE COMPILATIONWITHIN A CLOUD-BASED CONTENT HUB ENVIRONMENT”, Application No.62/900,266, filed Sep. 13, 2019, which application is hereinincorporated by reference.

This application is related to and incorporates by reference thefollowing applications: U.S. patent application entitled “SYSTEM ANDMETHOD FOR PROVIDING A USER INTERFACE FOR DYNAMIC SITE COMPILATIONWITHIN A CLOUD-BASED CONTENT HUB ENVIRONMENT” (Attorney Docket No.ORACL-05967US1), application No. ______/______,______, filed Sep. 11,2020; U.S. patent application entitled “SYSTEM AND METHOD FOR AUTOMATICSUGGESTION FOR DYNAMIC SITE COMPILATION WITHIN A CLOUD-BASED CONTENT HUBENVIRONMENT” (Attorney Docket No. ORACL-05967US3), application No.______/______,______, filed Sep. 11, 2020; and U.S. patent applicationentitled “SYSTEM AND METHOD FOR AUTOMATIC SELECTION FOR DYNAMIC SITECOMPILATION WITHIN A CLOUD-BASED CONTENT HUB ENVIRONMENT” (AttorneyDocket No. ORACL-05967US4), application No. ______/______,______, filedSep. 11, 2020; each of which applications are herein incorporated byreference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF INVENTION

This disclosure relates generally to website development; and moreparticularly, to systems and methods for dynamic site compilation fordistributed website development within a cloud-based content hubenvironment.

BACKGROUND

During the development of any given website, especially those websitesdriven by content, as well as updates to the content, there aregenerally two ways in which to ensure that the website content isdelivered to a viewer of a website. These two methods included dynamicfetching of content from a remote location, as well as the staticcaching of content at a local storage.

In accordance with an embodiment, static content can generally bethought of as a file that is stored on the server side of a website(e.g., in a local storage), and is presented in a same manner every timethe content is delivered to a viewer of the website. Examples of suchstatic content include, but are not limited to, images, gifs, HTML, andother types of content that generally do not change between differentloads of a given website. Static content can be considered to be like aprinted publication—once the content has been printed, it is generallynot changed or updated. One of the advantages of static content is thatit generally loads very quickly as it is stored a local storage.

In accordance with an embodiment, conversely, dynamic content is contentthat generally changes due to specific factors of a user at each visit,or content that changes due to updated or changing content creation on awebsite. Generally, websites that heavily rely upon dynamic content canchange from load to load of a website, due to, for example, a team ofcontent creators updating and publishing updates to a website in realtime. While dynamic content provides the advantage that a website canstay up to date from between subsequent loads of a website (orpush-refreshes), such content generally loads more slowly than cachedcontent as such dynamic content is stored at a remote location to thewebsite server.

More and more, today's websites comprise a mix of both static anddynamic content, while website developers are generally less technicallyminded. As such, it is becoming increasingly important to deliver amechanism that can allow a non-technical content developer to optimizehis or her website in a manner that will provide the best, and mostupdated (in terms of content), experience to an end user visiting such awebsite.

SUMMARY

In accordance with an embodiment, the presently disclosed embodimentsallow a non-technical user, as well as technical users, such as websitedevelopers, to “mark”, or flag, various components of a website or page.One category of such marks or flags can indicate that such items markedor flagged with this category of are to be dynamically loaded uponwebsite access (e.g., fetched from a source and then loaded into awebsite for viewing), while another category of mark or flag canindicate items so marked to be fixed at compile time (e.g., staticcache, that is the content is compiled within the published website).

In accordance with an embodiment, the cost of complex content managementsystem (CMS) queries can be reduced in the running site by electing tohave certain components compiled into the page (static cache). The CMSquery is then executed during compilation and results inserted directlyinto the compiled page. This results in better user experience andallows for very large scalability by offloading repetitive calls to theCMS server.

In accordance with an embodiment, additionally disclosed herein is anAI/ML engine (also referred to variously herein as an AI/ML analyticsengine, and analytics engine) that can utilize both content andconsumption analytics in providing suggested tags to a user, and/orautomatically tag certain components and content items of a websitebased upon, for example, a confidence score.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a system or archive file check-in/out in anenterprise content management system, in accordance with an embodiment.

FIG. 2 illustrates a system or archive file check-in/out in anenterprise content management system, in accordance with an embodiment.

FIG. 3 shows a system for dynamic site compilation in a cloud-basedcontent hub environment, in accordance with an embodiment.

FIG. 4 shows a system for dynamic site compilation in a cloud-basedcontent hub environment, in accordance with an embodiment.

FIG. 5 shows a system for dynamic site compilation in a cloud-basedcontent hub environment, in accordance with an embodiment.

FIG. 6 shows a flowchart of a suggestion engine and automatic taggingengine for use in dynamic site compilation in a cloud-based content hubenvironment, in accordance with an embodiment.

FIG. 7 shows a flowchart of a suggestion engine and automatic taggingengine for use in dynamic site compilation in a cloud-based content hubenvironment, in accordance with an embodiment.

FIG. 8 shows a flowchart of a suggestion engine and automatic taggingengine for use in dynamic site compilation in a cloud-based content hubenvironment, in accordance with an embodiment.

FIG. 9 is a flowchart of a method for a suggestion engine and automatictagging engine for use in dynamic site compilation in a cloud-basedcontent hub environment, in accordance with an embodiment.

FIG. 10 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 11 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 12 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 13 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 14 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 15 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 16A is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 16B is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 16C is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

FIG. 17 illustrates a process for compilation of components inaccordance with an embodiment.

FIG. 18 is a flowchart of a method for providing a user interface fordynamic site compilation in a cloud-based content hub environment, inaccordance with an embodiment.

FIG. 19 is a flowchart of a method for providing custom componentcompilation within a cloud-based content hub environment, in accordancewith an embodiment.

FIG. 20 is a flowchart of a method for automatic selection for dynamicsite compilation in a cloud-based content hub environment, in accordancewith an embodiment.

FIG. 21 is a flowchart of a method for automatic suggestion for dynamicsite compilation in a cloud-based content hub environment, in accordancewith an embodiment.

DETAILED DESCRIPTION

The foregoing, together with other features, will become apparent uponreferring to the enclosed specification, claims, and drawings. Specificdetails are set forth in order to provide an understanding of variousembodiments. However, it will be apparent that various embodiments maybe practiced without these specific details. The enclosed specificationand drawings are not intended to be restrictive.

In accordance with an embodiment, content management systems enablecontent to be created, uploaded, accessed, and modified by a pluralityof users. For example, a content item such as a document can be createdand uploaded by one user, and subsequently accessed and modified byother users. Additionally, a single document can be accessed (e.g.,viewed) concurrently by multiple users. Content management systems canbe useful for enterprises in which, for example, several individualscollaborate on a project by accessing the same document or set ofdocuments.

Complexities can arise, however, when a user wishes to upload multiplecontent items. In such situations, the user can generally be presentedwith an option to create an archive file (e.g., zip file, or otherarchive file type that merges/compresses multiple content files into asingle file) so that all the files to be uploaded to an ECM applicationand perform a single check-in operation in order avoid multiple check-inoperations that would be required if each content item was uploadedindividually. However, the uploaded archive file not exploded by an ECMapplication into an easy to use hierarchy, nor are the content itemsrepresented outside of the archive file.

FIG. 1 illustrates a system or archive file check-in/out in anenterprise content management system, in accordance with an embodiment

As illustrated in FIG. 1, in accordance with an embodiment, for each ofa plurality of client devices 100, 102, and 104 having a user interface101, 103, 105 and physical device hardware 106, 107, 108 (e.g., CPU,memory), the client device can be provided with a content accessapplication 110, 111, 112 for execution thereon.

In accordance with an embodiment, the client device can communicate 162with an application server 130 that includes a physical computerhardware 131 (e.g. CPU, memory) and an enterprise content managementsystem 132.

In accordance with an embodiment, the content access application at theclient device can communicate with the enterprise content managementsystem via a network 160 (e.g., the Internet, or a cloud environment).The content access application can be configured to enable a user 150,152, 154 to view, upload, modify, delete, or otherwise access contentsuch as content items 120, 122, 124 at each client device. For example,new content can be added or uploaded to the enterprise contentmanagement system by a user interacting with the content accessapplication on an associated client device. The content can betransmitted to the enterprise content management system for storage.

In accordance with an embodiment, the enterprise content managementsystem can be or include a platform for consolidating content that canbe managed by a plurality of users of an enterprise. In accordance withan embodiment, the enterprise content management system can beconfigured to communicate with a content database 136 for storingcontent (or content items) 140, and can deliver the content to users viatheir client devices. In accordance with an embodiment, the contentdatabase can be a relational database management system (RDBMS), filesystem, or other data source which the enterprise content managementsystem can access. Content can include, for example, documents, files,e-mails, memos, images, videos, slide presentations, conversations, anduser profiles.

In accordance with an embodiment, the enterprise content managementsystem can be configured to associate metadata with the content.Metadata can include information about an item of content, such as itstitle, author, release date, historical data such as who has accessedthe item and when, a location where the content is stored, and the like.

In accordance with an embodiment, the metadata can be stored in ametadata database 138. In accordance with an embodiment, the enterprisecontent management system can be configured to communicate with themetadata database to access metadata stored therein, and to storemetadata generated by the system in the metadata database.

In accordance with an embodiment, the enterprise content managementsystem can also be configured to communicate with a search index 139.The search index can be configured to provide indexing and searching ofcontent and data stored in the content database and the metadatadatabase. In accordance with an embodiment, the search index can be arelational database management system (RDBMS) or a search tool such asOracle Secure Enterprise Search (Oracle SES).

In accordance with an embodiment, content stored within the contentdatabase can be checked out for modification by a user at the user'sclient device, and checked back in to the enterprise content managementsystem.

In accordance with an embodiment, a checked-out document can be lockedwhile checked out to a particular user, to prevent other users frommodifying the checked-out document. However, the system can beconfigured to permit viewing of the document by other users while it ischecked out. In accordance with an embodiment, new versions of contentcan be created and stored in the content database of the enterprisecontent management system.

In accordance with an embodiment, the enterprise content managementsystem can further include a content management application 133including a security component 142. The security component can includeor store a security data including user permissions and privileges withrespect to particular items of content and/or particular actions. Forexample, the security data can indicate that certain users are permittedto access and/or modify certain documents. As another example, thesecurity data can indicate that only certain users are permitted tocreate links between content items, to modify certain content items, orto delete content items.

FIG. 2 illustrates a system or archive file check-in/out in anenterprise content management system, in accordance with an embodiment.

In accordance with an embodiment, in general, an Enterprise ContentManagement 210 system comprises a repository to store contents (e.g.,database 215) and allow access to these stored content items as and whenrequired via the ECM. Frequently performed operations by users 201, 202of the ECM system can comprise check-in and checkout operations, as wellas operations utilizing content items stored in a database 215, such asusing content items on published websites. The access permissions oncontent items can vary from Read, Write, Delete and Admin depending uponUser privileges.

In accordance with an embodiment, a content management system, such asan enterprise content management system described above, can form partof a cloud-based content hub.

In accordance with an embodiment, a cloud-based content hub can allowusers to manage content and digital assets via a network 205 connection(e.g., location independent). In addition, such a content hub allowsusers to store files in a cloud environment, allow access to such filesno matter the location of a user.

In accordance with an embodiment, a cloud-based content hub can providefor easy-to-use collaboration and workflow management in order tostreamline the creation and delivery of content to improve both customerand employee engagement.

In accordance with an embodiment, current website development and mediaaccess is centered more and more around content. Content is at the heartof almost all marketing and sales efforts. Users within a cloud-basedcontent hub can share, collaborate, process, and manage content easilyand effectively. Users can generally access such hubs via any networkconnected computer, tablet, or smartphone. Users can manage content justas if the content was residing on a local drive, and can add, deleted,and move files as needed within the hub. A cloud-based content hub canalso be a place for collaboration, where a content creator mightgenerate a piece to be published, pending approval by an editor. Forexample, if a picture needs to be approved before use on a website, aneditor, or other user with sufficient credentials, can view it on(again, on any device), approve it, and move it through the design andpublishing processes.

In accordance with an embodiment, a cloud-based content hub canadditionally provide for sharing of individual files, and even entirefolders with other users of the content hub, provided security andidentify clearances have been managed. The content hub can additionallyprovide permissioned sharing, where a user uploading content to beshared can selectively share the content with only designated users. Acould-based content hub can additionally provide for the sharing andjoint development of websites and collections of digital assets, soother users have access to the content that's needed for a project.

In accordance with an embodiment, a cloud-based content hub can keepcontent synchronized between a user's local computer and the cloud.Users can install applications on their local devices that automaticallykeeps files synced across the cloud, and optionally, other user devices.Such sharing also contemplates the sharing of updates to documents, suchas user generated content.

In accordance with an embodiment, users can utilize the cloud-basedcontent hub to communicate with other users regarding files, folders,content items, or assets used in upcoming promotions, letting users postcomments about it. Such files can also be modified via an annotation,highlighting a specific point and making a comment about it. As well,the cloud-based content hub can be utilized to have user discourse, suchas a project lead allowing team members to exchange ideas about projectsand processes. Then, files, such as content, can be added to suchconversations, so that all participants can view, revise, suggestrevisions, and comment on the content.

In accordance with an embodiment, a cloud-based content hub can be usedfor workflows. Workflows can be set up to funnel content to theappropriate people for approval and revision, eliminating bottlenecks ina process flow. Streamlined process management and content sharing meanmore efficiency and less gaps in shared knowledge.

In accordance with an embodiment, a cloud-based content hub can be usedfor website creation, updating, and maintenance. Websites can be createdand reviewed as needed with out-of-the-box templates and themes. Userscan easily preview what a created site looks like on devices withdifferent screen. For an optimal mobile experience, page content isautomatically rearranged on smaller screens. Sites can use the mostup-to-date information and assets to produce always-current material.

In accordance with an embodiment, users can manage all the assets neededfor a website in one place and set up policies governing the use ofthose assets. This can allow website creators to use content and datafrom existing sources in an easy manner.

In accordance with an embodiment, a cloud-based content hub can be usedto publish and update websites and make them available immediately.Users can work on one or more updates, preview an update in the site,and then publish the update with a single click.

In accordance with an embodiment, users can create content items, suchas articles or blog posts or listings, and publish the items on awebsite or in a brochure or wherever they're needed. Different layoutsmean that the content exists separately from the format, freeing usersto update content as needed without worrying about how it will look orwhether it will fit on the page.

Dynamic Site Compilation

In accordance with an embodiment, a cloud-based content hub can providea visual website assembly tool for knowledge workers (i.e.,non-technical users) to build sites through drag-and-drop of componentsonto pages. The user's actions in building a website can use metadata todefine the page, which is then rendered dynamically at runtime.

In accordance with an embodiment, because the runtime pages aredynamically rendered, such websites can suffer from several performanceissues, including but not limited to:

-   -   Delay on page start up to load up the page's meta-data before        knowing what to render on the page.    -   Flash of un-styled content (FOUC) while the page waits for all        CSS to load before being able to render.    -   Page animation (jumping) as components render at different        speeds in different locations on the page    -   Additional server load by every client querying for resources        that are not changing impact the overall page rendering speed.

In accordance with an embodiment, one solution to such problems involvesserver-side component rendering (on a per-request basis). When a requestis made, a dynamic component is given the opportunity to “pre-render”into the page so that the initial view of the page is mostly what isrequired. Additional client-side hydration can then be applied to thesepre-rendered components.

In accordance with an embodiment, another solution to such problems isstatic site generation (developer-centric). A site is created by adeveloper, who may use tools to compile a static version of the site.Another example is static site generation (non-technical user centric).Non-technical users building out the site using UI tools. Duringpublishing of a website, the dynamic data is converted to runtime dataand optimized for performance. In addition, there are JSP/PHP/ . . .per-request page generation tools that can be used for such purposes.

In accordance with an embodiment, however, the presently disclosedembodiment allows a non-technical user, as well as technical users, suchas website developers, to “mark”, or flag, various components of awebsite or page. One category of such marks or flags can then indicatethat such items marked or flagged with this category can continue to bedynamic (i.e., dynamically rendered on website load or refresh), whileanother category of marks or flags can indicate items so marked to befixed at compile time (e.g., static cache).

In accordance with an embodiment, the cost of complex content managementsystem (CMS) queries can be eliminated in the running site by electingto have the component compiled into the page (static cache). The CMSquery is then executed during compilation and results inserted directlyinto the compiled page. This results in far better user experience andallows for very large scalability by offloading repetitive calls to theCMS server.

Component Compilation

In accordance with an embodiment, the system allows developers to workwith a variety of technologies and optimize a page or site for runtimeperformance. For example, during site development, a customer'scomponent can be rendered with a framework such as VueJS, so that thecomponent can be dynamically added to the page and updated. Inaccordance with an embodiment, the developer can create a custom(component) compiler, for use during compilation of a particularcomponent, to convert the component to HTML/CSS so that it can beinjected into the page without the use of JavaScript.

In accordance with an embodiment, the addition of offline sitecompilation can provide up to, and sometimes surpassing, a 400% gain inload speed up to the point where the page starts to render. This isachieved by reducing the initial page load to a single request ratherthan several request building up the page HTML before the page can startrendering. This removes any product introduced issues with flash ofun-styled content (FOUC), allowing the template developer to havecontrol over how/when the page appears. This enhances the experience ofa user viewing the site as they navigate between pages in the site.

In accordance with an embodiment, for content-heavy pages, where suchcontent can be defined at compile time, the page rendering is immediateor near-immediate instead of needing to wait for the content queries toreturn and be available on the page. Not only does this provide the userviewing the page in the browser with a much better experience, it alsooffloads all the queries from the content server. That load is paid onceat compile, as opposed to on every single page request, resulting inmuch improved scalability.

FIG. 3 shows a system for dynamic site compilation in a cloud-basedcontent hub environment, in accordance with an embodiment.

In accordance with an embodiment, a cloud-based content hub 320, whichcan be run on a number of hardware and software resources 321 (e.g.,microprocessor, memory, storage, operation system . . . etc.), cancomprise a client interface 325 (e.g., a graphical user interface, acommand line interface, an application programming interface (API) . . .etc.), a content management system 322 (as described above), a server330, and a dynamic cache 340. Although shown as being part of thecloud-based content hub, the server 330, the content management system322, and the dynamic cache can be accessible by the content hub insteadof being thought of as logically comprising first level components ofthe content hub.

In accordance with an embodiment, a client device or user machine 305,which can be accessed and utilized by user 300, can comprise devicehardware (processor, memory . . . etc.) and software 315, as well as anapplication as content hub application 310, which can be used tocommunicate with the cloud-based content hub environment via a network,such as a wide area network (WAN), a local area network (LAN), or theinternet, for example. The content-hub application can comprise a userinterface, not shown.

In accordance with an embodiment, a user can utilize the content-hubapplication, and via the client interface 325, for example, uploadcontent (e.g., user generated content such as articles, pictures, videos. . . etc.) to the content hub, at, for example, the content managementsystem. Such upload and/or synchronization can be performed via a manualrequest, or via an automatic process that is signal by the content hubapplication, or by an instruction received from the client interface325. The user may also utilize the content hub application and/or theclient interface 325 to view, modify, edit, delete, or collaborate oncontent stored within the content management system, so long as the userhas properly authenticated with the content hub (such authenticationsystems are not shown in FIG. 3).

In accordance with an embodiment, a user may also utilize a websitedevelopment kit 326 of the client interface 325 to develop and publish awebsite via server 330. (The website developers kit, in otherembodiments, may be standalone service offered by the content hub. Forthe sake of convenience, the kit 326 is shown as being part of theclient interface in the presently described embodiment).

In accordance with an embodiment, as described above, the websitedevelopment kit can provide a plurality of website templates, as well asthe ability to drag and drop various items onto such templates, suchthat a non-technical user 300 can use the tools provided with ease.Examples of such development tools can be seen at FIGS. 10-16.

In accordance with an embodiment, the website development kit canprovide a website pane in which, based upon received inputs, variouspre-made templates and items can be placed (e.g., via drag and drop),onto a website template, which can then be, for example, previewedand/or published to the server 330 based upon received commands.

In accordance with an embodiment, because the website development kitcan interact with the content management system, any items of contentwithin the content management system that a user can access can also beprovided as items which can be placed onto a website template. Forexample, if one member of a team is working on an article within thecontent management system, another member of the team can use suchcontent in developing a website by placing an item comprising saidcontent within a template provided by the website development kit.

In accordance with an embodiment, the website development kit canadditionally provide an item tagging component that can received inputsfrom, for example, a user to tag certain items of a website as to bedynamically cached, while other items that are placed within adeveloping website can be tagged as static cache.

In accordance with an embodiment, then, items of content tagged asstatic can be stored at/compiled with a website at server 330 (e.g.,stored in cache 335), such that on a load or refresh of the website, theserver does not have to communicate with additional entities to gatherthe statically tagged content to be displayed or rendered on thewebsite.

In accordance with an embodiment, items tagged as to be staticallycached can be, on compiling the website, be stored 360 in a cache 335 atthe server 330 where the website is compiled. Examples of items to bestatically cached include items on a website that would not oftenchange, as such items would only be allowed to change upon are-compiling or re-publishing of a website, and not merely on a refreshof a webpage as performed by a viewer of the published website.

In accordance with an embodiment, items tagged as to be dynamicallycached can be stored 361 at, for example the dynamic cache/websitecontent database 340, or can be stored at the content management system322. Examples of items to be statically cached include items on awebsite that are subject to frequent changes, as such items would beallowed to change on a refresh of a webpage as performed by a viewer ofthe published website. As an example, an article that is being revisedand/or updated as a story develops. If such an article were being workedon within the content management system, a user, via the websitedevelopment kit, could place an item within the subject website templatethat corresponds to said story, and tag the item as dynamic. Then, asthe content is updated, the content on the published website is likewiseupdated 362 upon a refresh, or a push refresh, of the website at theserver 330.

In accordance with an embodiment, items that are tagged to bedynamically cached can be fetched from either the content managementsystem 322 or the dynamic cache 340 upon, for example, a load or arefresh of a website at server 330.

FIG. 4 shows a system for dynamic site compilation in a cloud-basedcontent hub environment, in accordance with an embodiment.

In accordance with an embodiment, a cloud-based content hub 420, whichcan be run on a number of hardware and software resources 421 (e.g.,microprocessor, memory, storage, operation system . . . etc.), cancomprise a client interface 425 (e.g., a graphical user interface, acommand line interface, an application programming interface (API) . . .etc.), a content management system 422 (as described above), a server430, a dynamic cache 440, and an artificial intelligence/machinelearning (AI/ML) engine 450 and an associated store/cache 451, at whichcan be stored and updated a training database. Although shown as beingpart of the cloud-based content hub, the server 430, the contentmanagement system 422, and the dynamic cache can be accessible by thecontent hub instead of being thought of as logically comprising firstlevel components of the content hub.

In accordance with an embodiment, a client device or user machine 405,which can be accessed and utilized by user 400, can comprise devicehardware (processor, memory . . . etc.) and software 415, as well as anapplication as content hub application 410, which can be used tocommunicate with the cloud-based content hub environment via a network,such as a wide area network (WAN), a local area network (LAN), or theinternet, for example. The content-hub application can comprise a userinterface, not shown.

In accordance with an embodiment, a user can utilize the content-hubapplication, and via the client interface 425, for example, uploadcontent (e.g., user generated content such as articles, pictures, videos. . . etc.) to the content hub, at, for example, the content managementsystem. Such upload and/or synchronization can be performed via a manualrequest, or via an automatic process that is signal by the content hubapplication, or by an instruction received from the client interface425. The user may also utilize the content hub application and/or theclient interface 425 to view, modify, edit, delete, or collaborate oncontent stored within the content management system, so long as the userhas properly authenticated with the content hub.

In accordance with an embodiment, a user may also utilize a websitedevelopment kit 426 of the client interface 425 to develop and publish awebsite via server 430. (The website developers kit, in otherembodiments, may be standalone service offered by the content hub. Forthe sake of convenience, the kit 426 is shown as being part of theclient interface in the presently described embodiment).

In accordance with an embodiment, as described above, the websitedevelopment kit can provide a plurality of website templates, as well asthe ability to drag and drop various items onto such templates, suchthat a non-technical user 400 can use the tools provided with ease.

In accordance with an embodiment, the website development kit canprovide a website pane in which, based upon received inputs, variouspre-made templates and items can be placed (e.g., via drag and drop),onto a website template, which can then be, for example, previewedand/or published to the server 430 based upon received commands.

In accordance with an embodiment, because the website development kitcan interact with the content management system, any items of contentwithin the content management system 422 that a user can access can alsobe provided as items which can be placed (e.g., drag and drop) onto awebsite template. For example, if one member of a team is working on anarticle within the content management system, another member of the teamcan use such content in developing a website by placing an itemcomprising said content within a template provided by the websitedevelopment kit.

In accordance with an embodiment, the website development kit canadditionally provide an item tagging component that can received inputsfrom, for example, a user to tag certain items of a website as to bedynamically cached, while other items that are placed within adeveloping website can be tagged as static cache. Such a tag cancomprise metadata attached to the content items.

In accordance with an embodiment, then, items of content tagged asstatic can be stored at/compiled with a website at server 430 (e.g.,stored in cache 435), such that on a load or refresh of the website, theserver does not have to communicate with additional entities to gatherthe statically tagged content to be displayed or rendered on thewebsite. In this way, a visitor to a website 470, utilizing a visitormachine 471, can view and interact with the website. On load or refreshof the website, items that are statically tagged will load faster thanthose that are dynamically fetched on load/refresh.

In accordance with an embodiment, items tagged as to be dynamicallycached can be stored 461 at, for example the dynamic cache/websitecontent database 440, or can be stored at the content management system422. Examples of items to be statically cached include items on awebsite that are subject to frequent changes, as such items would beallowed to change on a refresh of a webpage as performed by a viewer ofthe published website. As an example, an article that is being revisedand/or updated as a story develops. If such an article were being workedon within the content management system, a user, via the websitedevelopment kit, could place an item within the subject website templatethat corresponds to said story, and tag the item as dynamic. Then, asthe content is updated, the content on the published website is likewiseupdated 462 upon a refresh, or a push refresh, of the website at theserver 430.

In accordance with an embodiment, items that are tagged to bedynamically cached can be fetched from either the content managementsystem 422 or the dynamic cache 440 upon, for example, a load or arefresh of a website at server 430, e.g., from a visitor 470 via avisitor machine 471 viewing or loading the website compiled at theserver 430.

In accordance with an embodiment, items tagged as to be staticallycached can be, on compiling the website, be stored 460 in a cache 435 atthe server 430 where the website is compiled. Examples of items to bestatically cached include items on a website that would not oftenchange, as such items would only be allowed to change upon are-compiling or re-publishing of a website, and not merely on a refreshof a webpage as performed by a viewer of the published website.

In accordance with an embodiment, items tagged as to be dynamicallycached can be stored 461 at, for example the dynamic cache/websitecontent database 440, or can be stored at the content management system422. Examples of items to be statically cached include items on awebsite that are subject to frequent changes, as such items would beallowed to change on a refresh of a webpage as performed by a viewer ofthe published website. As an example, an article that is being revisedand/or updated as a story develops. If such an article were being workedon within the content management system, a user, via the websitedevelopment kit, could place an item within the subject website templatethat corresponds to said story, and tag the item as dynamic. Then, asthe content is updated, the content on the published website is likewiseupdated 462 upon a refresh, or a push refresh, of the website at theserver 430.

In accordance with an embodiment, the AI/ML engine 450 can monitor andtrack, via a content analytics engine (also referred to herein as ananalytics engine) of the AI/ML engine, the content analytics engineutilizing a knowledge database at a cache 435, the lifecycle of contentpublished at a website hosted at server 430. The metrics that can betracked by the content analytics engine can include, for example, thefrequency of publication (i.e., website loads or refreshes of pagescontaining the content items). The metrics that can be tracked by thecontent analytics engine can additionally include, for example, the rateof change of each content item published on the website (whether theitems are tagged static or dynamic). This tracking can be performed bymonitoring both the website at the server at its associated cache 435,and can additionally include monitoring the content management systemand the dynamical cache, for, e.g., the rate of updates to content itemsat, for example, the content management system 422 as well as dynamiccache 440. Additional metrics that can be tracked by a content analyticsengine of the AI/ML engine can include monitoring the usage/viewing ofcontent (e.g., the pervasiveness of usage) of the content, both at thewebsite (e.g., by viewer 470), as well as the individual usage ofcontent items at the content management system 422, the dynamic cache440, and the cache 435 of the server.

In accordance with an embodiment, such analytics engine can gatherinformation regarding, for example, popular pages of the publishedwebsite, popular content, pages where viewers spent the most time . . .etc.

Automatic Suggestion of Content based on Analytics

In accordance with an embodiment, the AI/ML engine, based upon themonitored metrics associated with content items, can provide one or moresuggestions 490 to a user 400, e.g., via the user machine 405, regardingwhich items of content would be most effective to be tagged as static,and which items of content would be most effective to be tagged asdynamic.

FIG. 5 shows a system for dynamic site compilation in a cloud-basedcontent hub environment, in accordance with an embodiment.

In accordance with an embodiment, a cloud-based content hub 520, whichcan be run on a number of hardware and software resources 521 (e.g.,microprocessor, memory, storage, operation system . . . etc.), cancomprise a client interface 525 (e.g., a graphical user interface, acommand line interface, an application programming interface (API) . . .etc.), a content management system 522 (as described above), a server530, a dynamic cache 540, and an artificial intelligence/machinelearning (AI/ML) engine 550 and an associated store/cache 551, at whichcan be stored and updated a training database. Although shown as beingpart of the cloud-based content hub, the server 530, the contentmanagement system 522, and the dynamic cache can be accessible by thecontent hub instead of being thought of as logically comprising firstlevel components of the content hub.

In accordance with an embodiment, a client device or user machine 505,which can be accessed and utilized by user 500, can comprise devicehardware (processor, memory . . . etc.) and software 515, as well as anapplication as content hub application 510, which can be used tocommunicate with the cloud-based content hub environment via a network,such as a wide area network (WAN), a local area network (LAN), or theinternet, for example. The content-hub application can comprise a userinterface, not shown.

In accordance with an embodiment, a user can utilize the content-hubapplication, and via the client interface 525, for example, uploadcontent (e.g., user generated content such as articles, pictures, videos. . . etc.) to the content hub, at, for example, the content managementsystem. Such upload and/or synchronization can be performed via a manualrequest, or via an automatic process that is signal by the content hubapplication, or by an instruction received from the client interface525. The user may also utilize the content hub application and/or theclient interface 525 to view, modify, edit, delete, or collaborate oncontent stored within the content management system, so long as the userhas properly authenticated with the content hub.

In accordance with an embodiment, a user may also utilize a websitedevelopment kit 526 of the client interface 525 to develop and publish awebsite via server 530. (The website developers kit, in otherembodiments, may be standalone service offered by the content hub. Forthe sake of convenience, the kit 526 is shown as being part of theclient interface in the presently described embodiment).

In accordance with an embodiment, as described above, the websitedevelopment kit can provide a plurality of website templates, as well asthe ability to drag and drop various items onto such templates, suchthat a non-technical user 500 can use the tools provided with ease.

In accordance with an embodiment, the website development kit canprovide a website pane in which, based upon received inputs, variouspre-made templates and items can be placed (e.g., via drag and drop),onto a website template, which can then be, for example, previewedand/or published to the server 530 based upon received commands.

In accordance with an embodiment, because the website development kitcan interact with the content management system, any items of contentwithin the content management system 522 that a user can access can alsobe provided as items which can be placed (e.g., drag and drop) onto awebsite template. For example, if one member of a team is working on anarticle within the content management system, another member of the teamcan use such content in developing a website by placing an itemcomprising said content within a template provided by the websitedevelopment kit.

In accordance with an embodiment, the website development kit canadditionally provide an item tagging component that can received inputsfrom, for example, a user to tag certain items of a website as to bedynamically cached, while other items that are placed within adeveloping website can be tagged as static cache. Such a tag cancomprise metadata attached to the content items.

In accordance with an embodiment, then, items of content tagged asstatic can be stored at/compiled with a website at server 530 (e.g.,stored in cache 535), such that on a load or refresh of the website, theserver does not have to communicate with additional entities to gatherthe statically tagged content to be displayed or rendered on thewebsite. In this way, a visitor to a website 570, utilizing a visitormachine 571, can view and interact with the website. On load or refreshof the website, items that are statically tagged will load faster thanthose that are dynamically fetched on load/refresh.

In accordance with an embodiment, items tagged as to be dynamicallycached can be stored 561 at, for example the dynamic cache/websitecontent database 540, or can be stored at the content management system522. Examples of items to be statically cached include items on awebsite that are subject to frequent changes, as such items would beallowed to change on a refresh of a webpage as performed by a viewer ofthe published website. As an example, an article that is being revisedand/or updated as a story develops. If such an article were being workedon within the content management system, a user, via the websitedevelopment kit, could place an item within the subject website templatethat corresponds to said story, and tag the item as dynamic. Then, asthe content is updated, the content on the published website is likewiseupdated 562 upon a refresh, or a push refresh, of the website at theserver 530.

In accordance with an embodiment, items that are tagged to bedynamically cached can be fetched from either the content managementsystem 522 or the dynamic cache 540 upon, for example, a load or arefresh of a website at server 530, e.g., from a visitor 570 via avisitor machine 571 viewing or loading the website compiled at theserver 530.

In accordance with an embodiment, items tagged as to be staticallycached can be, on compiling the website, be stored 560 in a cache 535 atthe server 530 where the website is compiled. Examples of items to bestatically cached include items on a website that would not oftenchange, as such items would only be allowed to change upon are-compiling or re-publishing of a website, and not merely on a refreshof a webpage as performed by a viewer of the published website.

In accordance with an embodiment, items tagged as to be dynamicallycached can be stored 561 at, for example the dynamic cache/websitecontent database 540, or can be stored at the content management system522. Examples of items to be statically cached include items on awebsite that are subject to frequent changes, as such items would beallowed to change on a refresh of a webpage as performed by a viewer ofthe published website. As an example, an article that is being revisedand/or updated as a story develops. If such an article were being workedon within the content management system, a user, via the websitedevelopment kit, could place an item within the subject website templatethat corresponds to said story, and tag the item as dynamic. Then, asthe content is updated, the content on the published website is likewiseupdated 562 upon a refresh, or a push refresh, of the website at theserver 530.

In accordance with an embodiment, the AI/ML engine 550 can monitor andtrack, via a content analytics engine of the AI/ML engine, the contentanalytics engine utilizing a knowledge database at a cached 535, thelifecycle of content published at a website hosted at server 530. Themetrics that can be tracked by the content analytics engine can include,for example, the frequency of publication (i.e., website loads orrefreshes of pages containing the content items). The metrics that canbe tracked by the content analytics engine can additionally include, forexample, the rate of change of each content item published on thewebsite (whether the items are tagged static or dynamic). This trackingcan be performed by monitoring both the website at the server at itsassociated cache 535, and can additionally include monitoring thecontent management system and the dynamical cache, for, e.g., the rateof updates to content items at, for example, the content managementsystem 522 as well as dynamic cache 540. Additional metrics that can betracked by a content analytics engine of the AI/ML engine can includemonitoring the usage/viewing of content (e.g., the pervasiveness ofusage) of the content, both at the website (e.g., by viewer 570), aswell as the individual usage of content items at the content managementsystem 522, the dynamic cache 540, and the cache 535 of the server.

In accordance with an embodiment, such analytics engine can gatherinformation regarding, for example, popular pages of the publishedwebsite, popular content, pages where viewers spent the most time . . .etc.

In accordance with an embodiment, the AI/ML engine, based upon themonitored metrics associated with content items, can automatically markcertain content as static 590 (i.e., compiled along with the website andstored in cache 535), and can automatically mark certain other contentas dynamic 591 (i.e., to be stored in a dynamic cache 540, or at thecontent management system 522). Such automatic tagging of content itemsas either static or dynamic can be made upon a determination, by acontent analytics engine (of the AI/ML engine) regarding which items ofcontent would be most effective to be tagged as dynamic and whichcontent items would be most effective as being tagged static.

FIG. 6 shows a flowchart of a suggestion engine for use in dynamic sitecompilation in a cloud-based content hub environment, in accordance withan embodiment.

In accordance with an embodiment, as discussed above, the websitedevelopment kit discussed above can work in conjunction with asuggestion and automatic tagging engine to be used in tagging variouswebsite elements as dynamic or static.

In accordance with an embodiment, at step 650, content authors, such asuser 600, can manage and publish content to a cloud-based content hub,via, for example, a client interface. Such content can be managed andpublished at a content management and publishing system 605, which, forexample, can comprise a content management system as described above.

In accordance with an embodiment, at step 651, via a content analyticsengine 640, which can be based upon, for example, artificialintelligence and machine learning via a knowledge database, can trackthe published content's lifecycle analytics 610. Such tracking metricscan include the frequency of publication, the rate of change of thecontent, content categorization, scheduled publish activity, andsimilarity with other qualified content (e.g., content that previouslywent through static complication).

In accordance with an embodiment, at step 652, content authors, such asuser 600, can utilize a website authoring interface 615, such as thewebsite development kit, in order to design and build a website via, forexample, supplied website templates and drag and drop functionality toplace various items, including published content from step 650, to adraft website.

In accordance with an embodiment, at step 653, the user 600 can build620 (e.g., compile, package, and optimize) a website, prior topublication (before the website is made available to public viewing, orinternal viewing by others with allowed access). Such website can be,for example, previewed by the author, then revised, and previewed again.

In accordance with an embodiment, at step 654, the website can bepublished (as a compiled website 625) to a, for example, publiclyaccessible server, which can be accessed 655 by website viewers 630. Asdescribed above, the compiled website 625 can comprise both content thatis both tagged as static (e.g., content items compiled with the websiteas static content and not fetched from an alternative source on websiteload/refresh) or dynamic content (e.g., content items not compiled withthe website as static content and are rather fetched from an alternativesource, such as a content management system 605 or a dynamic cache, onwebsite load/refresh).

In accordance with an embodiment, a consumption analytics engine 635can, at step 656, gather website visitor/website behavior with respectto the website as the website viewers 640 interact with the publishedwebsite. Such analytics engine can gather information regarding, forexample, popular web pages, popular content on a web page, engagement(time spent on page/content, repeated views by same user, bounce rate),direct access pages (e.g., direct page access from, e.g., a searchengine result), custom conversions.

In accordance with an embodiment, at step 657, an ArtificialIntelligence/Machine Learning tag engine 640 can monitor the collectedanalytics from steps 651 and 656 in order to produce recommendations 658regarding tagging (static versus dynamic) decisions. The engine 640 canbe associated with a knowledge database (not shown) that can comprise aset of seed data, and which can be built upon based upon metricsanalyzed, as well as an analysis of the accuracy of the output of theengine 640.

In accordance with an embodiment, the engine 640 can present optimizedtagging suggestions/recommendations to a site author at step 658 (e.g.,via the website authoring interface 615).

In accordance with an embodiment, the AI/ML engine constantly monitorsboth content analytics as well as consumption analytics. Thus, theengine 640 is capable of revising and changing prior tagsuggestions/decisions based upon the analysis of subsequent metrics(metrics produced after an initial tag suggestion/decision).

In accordance with an embodiment, the AI/ML engine can perform ananalysis such as the example illustrated below:

Content qualification metrics:

-   -   1. Frequency of publication (CQw1)    -   2. Rate of change of content (CQw2)    -   3. Content categorization (CQw3)    -   4. Schedule publish activity (CQw4)    -   5. Similarity with other qualified content (content that        previously went through static compilation) (CQw5)    -   ==Content Qualification (CQ)=fn (CQw1, CQw2, CQw3, CQw4, CQw5)        Usage qualification metrics:    -   1. Popular pages (UQw1)    -   2. Popular content (UQw2)    -   3. Engagement (time spent on page/content, repeated views by        same user, bounce rate) (UQw3)    -   4. Direct access pages (e.g., direct page access from, e.g., a        search engine result) (UQw4)    -   5. Custom conversions (UQw5)    -   ==Usage Qualification (UQ)=fn (UQw1, UQw2, UQw3, UQw4, UQw5)        Wherein the AI/ML engine performs a process:    -   1. For each content item in the system:        -   a. Compute CQ and UQ continuously.    -   2. Periodically compute:        -   a. Generate a list of top candidates (content items) for            static compilation.        -   b. Suggest/automatically tag for static compilation based on            generated list of top candidates.

Automatic Selection of Content Based on Analytics

FIG. 7 shows a flowchart of an automatic tagging engine for use indynamic site compilation in a cloud-based content hub environment, inaccordance with an embodiment.

In accordance with an embodiment, as discussed above, the websitedevelopment kit discussed above can work in conjunction with asuggestion and automatic tagging engine to be used in tagging variouswebsite elements as dynamic or static.

In accordance with an embodiment, at step 750, content authors, such asuser 700, can manage and publish content to a cloud-based content hub,via, for example, a client interface. Such content can be managed andpublished at a content management and publishing system 705, which, forexample, can comprise a content management system as described above.

In accordance with an embodiment, at step 751, via a content analyticsengine 740, which can be based upon, for example, artificialintelligence and machine learning via a knowledge database, can trackthe published content's lifecycle analytics 710. Such tracking metricscan include the frequency of publication, the rate of change of thecontent, and the pervasiveness of usage of the content.

In accordance with an embodiment, at step 752, content authors, such asuser 700, can utilize a website authoring interface 715, such as thewebsite development kit, in order to design and build a website via, forexample, supplied website templates and drag and drop functionality toplace various items, including published content from step 750, to adraft website.

In accordance with an embodiment, at step 753, the user 700 can build720 (e.g., compile, package, and optimize) a website, prior topublication (before the website is made available to public viewing, orinternal viewing by others with allowed access). Such website can be,for example, previewed by the author, then revised, and previewed again.

In accordance with an embodiment, at step 754, the website can bepublished (as a compiled website 725) to a, for example, publiclyaccessible server, which can be accessed 755 by website viewers 730. Asdescribed above, the compiled website 725 can comprise both content thatis both tagged as static (e.g., content items compiled with the websiteas static content and not fetched from an alternative source on websiteload/refresh) or dynamic content (e.g., content items not compiled withthe website as static content and are rather fetched from an alternativesource, such as a content management system 705 or a dynamic cache, onwebsite load/refresh).

In accordance with an embodiment, a consumption analytics engine 735can, at step 756, gather website visitor/website behavior with respectto the website as the website viewers 740 interact with the publishedwebsite. Such analytics engine can gather information regarding, forexample, popular pages of the published website, popular content, pageswhere viewers spent the most time . . . etc.

In accordance with an embodiment, at step 757, an ArtificialIntelligence/Machine Learning tag engine 740 can monitor the collectedanalytics from steps 751 and 756 in order to automatically tag 758certain items of content as static or dynamic upon building a website.In this way, as opposed to presenting options to a user 700 with regardto what items of content should be tagged as static or dynamic, theengine 740 can itself make the decisions, thus simplifying the websitedesigning and building process for the user 700. The engine 740 can beassociated with a knowledge database (not shown) that can comprise a setof seed data, and which can be built upon based upon metrics analyzed,as well as an analysis of the accuracy of the output of the engine 740.

In accordance with an embodiment, the engine 740 can, based upon adetermination made as to the benefits of tagging one, some, or all itemsof content as either static or dynamic, make such tagging decisions andautomatically select a tag, based upon its analysis, of various items ona website, and compile the components into the website at step 758.

In accordance with an embodiment, the AI/ML engine constantly monitorsboth content analytics as well as consumption analytics. Thus, theengine 740 is capable of revising and changing prior tagsuggestions/decisions based upon the analysis of subsequent metrics(metrics produced after an initial tag suggestion/decision).

FIG. 8 shows a flowchart of an automatic tagging engine for use indynamic site compilation in a cloud-based content hub environment, inaccordance with an embodiment.

In accordance with an embodiment, as discussed above, the websitedevelopment kit discussed above can work in conjunction with asuggestion and automatic tagging engine to be used in tagging variouswebsite elements as dynamic or static.

In accordance with an embodiment, at step 850, content authors, such asuser 800, can manage and publish content to a cloud-based content hub,via, for example, a client interface. Such content can be managed andpublished at a content management and publishing system 805, which, forexample, can comprise a content management system as described above.

In accordance with an embodiment, at step 851, via a content analyticsengine 840, which can be based upon, for example, artificialintelligence and machine learning via a knowledge database, can trackthe published content's lifecycle analytics 810. Such tracking metricscan include the frequency of publication, the rate of change of thecontent, and the pervasiveness of usage of the content.

In accordance with an embodiment, at step 852, content authors, such asuser 800, can utilize a website authoring interface 815, such as thewebsite development kit, in order to design and build a website via, forexample, supplied website templates and drag and drop functionality toplace various items, including published content from step 850, to adraft website.

In accordance with an embodiment, at step 853, the user 800 can build820 (e.g., compile, package, and optimize) a website, prior topublication (before the website is made available to public viewing, orinternal viewing by others with allowed access). Such website can be,for example, previewed by the author, then revised, and previewed again.

In accordance with an embodiment, at step 854, the website can bepublished (as a compiled website 825) to a, for example, publiclyaccessible server, which can be accessed 855 by website viewers 830. Asdescribed above, the compiled website 825 can comprise both content thatis both tagged as static (e.g., content items compiled with the websiteas static content and not fetched from an alternative source on websiteload/refresh) or dynamic content (e.g., content items not compiled withthe website as static content and are rather fetched from an alternativesource, such as a content management system 805 or a dynamic cache, onwebsite load/refresh).

In accordance with an embodiment, a consumption analytics engine 835can, at step 856, gather website visitor/website behavior with respectto the website as the website viewers 840 interact with the publishedwebsite. Such analytics engine can gather information regarding, forexample, popular pages of the published website, popular content, pageswhere viewers spent the most time . . . etc.

In accordance with an embodiment, at step 857, an ArtificialIntelligence/Machine Learning tag engine 840 can monitor the collectedanalytics from steps 851 and 856 in order to automatically tag 858certain items of content as static or dynamic upon building a website.In this way, as opposed to presenting options to a user 800 with regardto what items of content should be tagged as static or dynamic, theengine 840 can itself make the decisions, thus simplifying the websitedesigning and building process for the user 800. The engine 840 can beassociated with a knowledge database (not shown) that can comprise a setof seed data, and which can be built upon based upon metrics analyzed,as well as an analysis of the accuracy of the output of the engine 840.

In accordance with an embodiment, a user can set the engine 840 with avariable confidence score index, where any tag suggestions below a setconfidence score can be provided to a user, at step 858, to make astatic/dynamic content tagging decision upon the confidence score notbeing met at 841. Upon a confidence score being met, at 841, the engine840 can automatically make the tagging decision 859, and such contentcan automatically be built into the website without user approval.

In accordance with an embodiment, the AI/ML engine constantly monitorsboth content analytics as well as consumption analytics. Thus, theengine 840 is capable of revising and changing prior tagsuggestions/decisions based upon the analysis of subsequent metrics(metrics produced after an initial tag suggestion/decision).

FIG. 9 is a flowchart of a method for an automatic tagging engine foruse in dynamic site compilation in a cloud-based content hubenvironment, in accordance with an embodiment.

In accordance with an embodiment, a site can be built and published at900. At 905, the site can be edited (or a page of the site).

In accordance with an embodiment, at 910, if the edit involves adding acomponent to the website, it can be checked at 915 whether the componentreferences a piece of content, such as from a content management systemof the cloud-based content hub. If not, then at 320, the item can betagged, or suggested to be tagged as to render during compile of thewebsite (static cache).

In accordance with an embodiment, if the component does reference acontent item, then the method can check, at 925, whether the contentitem is active. If not, then at 920, the item can be tagged, orsuggested to be tagged as to render during compile of the website(static cache). If so, then at 930, the item can be tagged, or suggestedto be tagged, as to render the item at runtime (dynamic cache).

In accordance with an embodiment, at 935, if the edit involves adding acontent item or digital asset, then the method can check, at 925,whether the content item is active. If not, then at 920, the item can betagged, or suggested to be tagged as to render during compile of thewebsite (static cache). If so, then at 930, the item can be tagged, orsuggested to be tagged, as to render the item at runtime (dynamiccache).

In accordance with an embodiment, at 940, if the edit involves adding acontent list to the website, it can be checked at 945 whether theresults of the content list are active. If not, then at 920, the itemcan be tagged, or suggested to be tagged as to render during compile ofthe website (static cache).

In accordance with an embodiment, if the results of the content list areactive, then at 930, the item can be tagged, or suggested to be tagged,as to render the item at runtime (dynamic cache).

User Interface

FIG. 10 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 10 shows is a screenshot of an exemplary websitedesign portal/toolkit as provided in a cloud-based content hub showing aplurality of site template options, in accordance with an embodiment.

FIG. 11 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 11 is a screen shot of exemplary website designportal/toolkit as provided in a cloud-based content hub showing aplurality of content assets that can be used within a designed website,in accordance with an embodiment. Such content assets can, for example,be stored at a content management system, as described above.

FIG. 12 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 12 is a screen shot of exemplary website designportal/toolkit as provided in a cloud-based content hub showing aplurality of content assets that can be used within a designed website,in accordance with an embodiment. Such content assets can, for example,be stored at a content management system, as described above.

FIG. 13 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 13 is a screen shot of exemplary website designportal/toolkit as provided in a cloud-based content hub showing aplurality of content assets that can be selected to be loaded, eitherstatically or dynamically, into a website design, in accordance with anembodiment. Such content assets can, for example, be stored at a contentmanagement system, as described above.

FIG. 14 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 14 is a screen shot of exemplary website designportal/toolkit as provided in a cloud-based content hub showing drag anddrop functionality of a content asset that can be selected to be loaded,either statically or dynamically, into a website design, in accordancewith an embodiment. Such content asset can, for example, be stored at acontent management system, as described above.

FIG. 15 is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 15 is a screen shot of exemplary website designportal/toolkit as provided in a cloud-based content hub showing acontent item that has been selected/tagged to either be staticallycompiled into a published website, or dynamically fetched upon websiteload, in accordance with an embodiment. In the displayed screen shot ofFIG. 9, the content list, “starter-blog-authors” can be designated asstatic and can be compiled into the published website such that loadtimes of the website are reduced.

FIG. 16A is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 16A is a screen shot of exemplary website designportal/toolkit as provided in a cloud-based content hub showing asettings window for a selected content item. The setting window providesflagging options to a user to optionally render the content item whenthe website is published. In some embodiments, such an option can beselected via user interaction. In other embodiments, as described above,an engine can provide a suggested tag for such content items, or caneven dynamically tag the content item without user interaction, again,as described above.

FIG. 16B is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 16B is a screen shot of exemplary website designportal/toolkit as provided in a cloud-based content hub showing asettings window for a selected content item. The Content Items Settingwindow can provide optimization hints 1610, e.g., upon a user ordeveloper hovering over or selecting an interactive icon within the userinterface. For example, the optimization hint can comprise, with respectto a selected content item on a page, a suggestion to render on publish(static) or render on load (dynamic). Such a suggestion 1610 can bebased upon the AI/ML engine's analysis of one of or both of consumptionor content analytics.

In accordance with an embodiment, in this way, the results of the AI/MLanalysis of consumption and content analytics is surfaced to, e.g., auser or developer, via a user interface, in a way that provides asuggestion to a user to select any given piece of content on a site tobe statically published (optimized) or left to be loaded dynamically, asdescribed above.

FIG. 16C is a screen shot of an exemplary website design portal/toolkitas provided in a cloud-based content hub, in accordance with anembodiment.

More particularly, FIG. 16C is a screen shot of exemplary website designportal/toolkit as provided in a cloud-based content hub showing asettings window for a selected content item. The Content Items Settingwindow can display an automatic/automated selection for optimization ofcontent on a website, e.g., upon a user or developer hovering over orselecting an interactive icon within the user interface. For example,the optimization hint can comprise, with respect to a selected contentitem on a page, an explanation regarding an AI/ML engine's decision tomark a selected content item as render on publish (static) or render onload (dynamic) based upon an analysis of consumption and contentanalytics. Such an explanation 1620 can be based upon the AI/ML engine'sanalysis of one of or both of consumption or content analytics.

In accordance with an embodiment, in this way, the results of the AI/MLanalysis of consumption and content analytics is surfaced to, e.g., auser or developer, via a user interface, in a way that provides anexplanation to a user that the systems selected a piece of content on asite to be statically published (optimized) or left to be loadeddynamically, as described above.

In accordance with an embodiment, a user or site developer can overridethe static/dynamic decision made by the system based upon the AI/ML'sanalysis of content and consumption analytics.

Automatic Selection of Dynamic or Static Data

In accordance with an embodiment, instead of providing a suggestion, thesystem makes a determination and selects the pieces of content to bestatically compiled. Such a decision making process can be based upon,e.g., a set of defined criteria (e.g., must have X level of certaintythat this content changes from page view to page view). This can beuseful, for example, when a content creator/marketer is being inundatedwith a voluminous number of options as presented by the aboveembodiment. In such cases, the option can be selected to have thesuggestion engine take over the decision-making process with regard tostatically compiled content.

Custom Components

As described above, in accordance with an embodiment, the system allowsdevelopers to work with a variety of technologies and optimize a page orsite for runtime performance, including in some instances the use of acustom (component) compiler, for use during compilation of a particularcomponent, to convert the component to HTML/CSS so that it can beinjected into the page without the use of JavaScript.

Examples of the types of components that can be added to a page includeparagraphs, titles, images, or dividers; which can be defined by localcomponent files, or remote component files. Local component files arestored in a local server, and can be set to render directly within apage, or in an inline frame in the page. Remote component files arestored on a remote server, and are always rendered in an inline frame.

In accordance with an embodiment, a component can be associated with aJavaScript JSON (render.js) file; and can be additionally associatedwith a template that describes how its content will be displayed, forexample within a site theme. Once added to a site, the developer canthen edit a component's property settings, to address requirements suchas page content, fonts and font sizes, image framing and placement, andother styles. For example, a local component can be defined as:

/Components/component-name appinfo.json _folder_icon.jpg assetssettings.html render.js

As another example, a local component using an inline frame can bedefined as:

/Components/component-name appinfo.json _folder_icon.jpg assetssettings.html render.js js sites.min.js knockout.min.js jquery.min.js

As another example, a remote component can be defined as:

/Components/component-name appinfo.json _folder_icon.jpg keys.json

In accordance with an embodiment, the developer can createcomponent-compilation-specific instructions for a particular component,which are passed during compilation and operate as a custom (component)compiler, to convert the particular component to HTML/CSS, so that thecomponent can subsequently be injected into the page. Alternatively, ifthere is a custom compiler defined for a particular component, then thecomponent-compilation-specific instructions associated with thatparticular component will be used to modify the resulting HTML to beinserted into the page. If there is no custom compiler defined for aparticular component, then the component will be rendered per the usualprocess, for example via the component's render.js file.

In accordance with an embodiment, a custom compiler can also indicatethat the component requires JavaScript “hydration” at runtime, in whichcase the component's hydrate( ) function within its render.js file willbe called. Alternatively, if the component does not require hydration,then the component's render.js file is not loaded.

FIG. 17 illustrates a process for compilation of components inaccordance with an embodiment.

As illustrated in FIG. 17, in accordance with an embodiment, at 1710, arequest is received to compile a site. For example, this can be a manualrequest, or it can be triggered automatically by editing of the site inthe user interface, or by any of the various embodiments of AI/MLsuggestion or prediction processes described above.

At 1712, a determination is made as to whether all pages have beencompiled, and if so then, at 1714, the compiled site is provided.

Otherwise, at 1720, each of the pages that comprise the site arecompiled. During compilation of a page, at 1722, a determination is madeas to whether a page template compiler exists. If so, then at 1724, thepage template is compiled. Otherwise at 1726, an existing page templatecan be used

At 1730, a determination is made as to whether all components arecompiled. If so, then at 1732, the page is compiled.

At 1740, each component instance that comprises the page are compiled.If, at 1742 a component is marked for compilation, and at 1744 acomponent compiler exists, then at 1760, the component is compiled.Otherwise, at 1750 the components is rendered at runtime.

Following compilation of all the components in the page, at 1770, theprocess is continued for each next page, until all of the pages in thesite have been compiled.

Page Layout Compilers

In accordance with an embodiment, a Page Layout Compiler is provided asa JavaScript module that compiles the corresponding Page Layout. ThePage Layout Compiler for a specific Page Layout is defined by nameassociation with a “-compile.js” extension:

src themes <yourTheme> layouts <yourPageLayout>.html<yourPageLayout>-compile.js

If no “-compile.js” exists for a page layout then no custom compilationis applied. A page layout compiler needs to implement a “compile( )”interface, which returns a promise. e.g.: about-compile.js:

var AboutPageCompiler = function ( ) { };AboutPageCompiler.prototype.compile = function (args) { var self = this,layoutMarkup = args.layoutMarkup; self.SCSCompileAPI =args.SCSCompileAPI; return new Promise(function (resolve, reject) { varcompiledPage = ‘’; // do some work to compile the page compiledPage =doSomeWork(layoutMarkup); // return the compiled pageresolve(compiledPage); }); }; module.exports = new AboutPageCompiler( );

Custom Compilers

In accordance with an embodiment, custom compilers are supported for:Page Layouts; Section Layouts; Custom Components; and Content Layouts.During compile, the compile-template command will look for a“compile.js” file in the same location as the “render.js” for thecomponent:

src components <yourComponent> assets render.js compile.js

If this file doesn't exist, the component is not compiled and will berendered at runtime. If the file does exist, it needs to implement a“compile( )” interface, which returns a promise. e.g.:

var fs = require(‘fs’), path = require(‘path’), mustache =require(‘mustache’); var UWContentHeader = function ( ) { };UWContentHeader.prototype.compile = function (args) { var compId =args.compId, customSettingsData = args.customSettingsData; return newPromise(function (resolve, reject) { try { var dir = _(——)dirname,templateFile = path.join(dir, ‘compile.html’), template =fs.readFileSync(templateFile, ‘utf8’); var model = { title:customSettingsData.title || ‘’, body: customSettingsData.body || ‘’ };var markup = ‘’; markup = mustache.render(template, model); returnresolve({ hydrate: false, content: markup }); } catch (e) {console.log(type + ‘: failed to expand template’); console.log(e); }return resolve({ }); }); }; module.exports = new UWContentHeader( );

Component Hydration

As described above, component compilers insert HTML into the page. If Acomponent needs additional JavaScript to be executed at runtime to addin things like event handlers, the on e approach is to InlineJavaScript, i.e., You can insert a <script> tag directly into thereturned compiled markup, which will execute as the page executes. e.g.:

<script src=“../_sitesclouddelivery/renderer/libs/scs- core/jssorslider/js/jssor.slider.min.js” type=“text/javascript”></script> <divid=“slider_container_c46b122d-978a-429d-aa25-9b5698428f6f”style=“position: relative; top: 0px; left: 0px; height: 400px; width:600px; background-color: rgb(68, 68, 68); visibility: visible;” data-jssorslider=“ 1”> ... </div> <script> (function ( ) { // get therequired options var options ={“$FillMode”:2,“$AutoPlay”:false,“$AutoPlayInterval”:3000,“$SlideDuration”:500,“$ArrowKeyNavigation”:true,“$HWA”:false,“$BulletNavigatorOptions”:{“$ChanceToShow”:1,“$AutoCenter”:1,“$SpacingX”:5},“$ArrowNavigatorOptions”:{“$ChanceToShow”:1,“$AutoCenter”:2,“$Steps”:1},“$ThumbnailNavigatorOptions”:{“$ChanceToShow”:0,“$Displaypieces”:7,“$SpacingX”:8,“$ParkingPosition”:240}}; //select the JSSOR value options options.$BulletNavigatorOptions.$Class =$JssorBulletNavigator$; options.$ArrowNavigatorOptions.$Class =$JssorArrowNavigator$; options.$ThumbnailNavigatorOptions.$Class =$JssorThumbnailNavigator$; // create the slider var slider = new$JssorSlider$(“slider_container_c46b122d-978a-429d-aa25-9b5698428f6f”,options); // resize, maintaining aspect ratio var container =slider.$Elmt.parentElement; if (container) {slider.$ScaleWidth(container.getBoundingClientRect( ).width); } })( );

Hydrate Function

In accordance with an embodiment, an alternative approach is to includea hydrate function in the render.js file and note that the componentrequires hydration at runtime when you return the compiled markup. Thisavoids repetitious <script> tags as well as enabling you to leverageexisting JavaScript code to managing eventing, e.g.:

return resolve({ hydrate: true, content: markup });

If a component notes that it needs hydration then, at runtime, thecomponent's render.js file will be loaded and the hydrate( ) functioncalled passing in the container <div> that contains the compiled markup,e.g.: render.hydrate( ):

this.hydrate = $.proxy(function (container) { var self = this,$container = $(container), $img = $container.find(‘scs-image’),$parentDiv = $img.parent( ); // hydrate the trigger events$parentDiv.click(function (event) {self.viewModel.imageClicked($parentDiv[0], event); }); // hydrate theaction handlers self.viewModel.imageWidth.subscribe(function(newImageWidth) { // calculate the new image style var style; if(self.viewModel.showTopLayout( )) { style = ‘’; } else { style =‘flex-shrink:0;width:’ + newImageWidth + ‘;’; } // update the sizingstyle $parentDiv.attr(‘style’, style); });

Compile-Template Command

In accordance with an embodiment, the system also supports the use of acompile-template command, for example as a run-time command, ortriggered by any of the AI/ML processes described above, which allowsthe developer (or system) to compile all of the site pages within atemplate, which pages can then be deployed to the site. Thecompile-template command has the following options:

cec compile-template <source>

The above command compiles all the pages within the site of the templateand places the compiled pages under the sites assets folder. Commandline options include, for example, the channel access token to use forcontent URLs, for example:

cec compile-template Temp1

Compiles the site in template Temp1, while:

cec compile-template Temp1 -c channelToken

Which causes the system compiles the site in template Temp1 using thegiven channelToken for any content URLs, including:

For each page in the site: Read in the site and page meta-data; Read inthe Page Layout and apply any page layout compiler.

For each slot on the page: Expand the slot with the grid defined in thepage.json file.

For each component within the slot: Apply any component compiler; andInsert the generated component markup in the corresponding locationwithin the slot.

Expand any macros in the compiled markup and insert the “SCS” JavaScriptobject that is used by the system renderer at runtime.

Save the compiled page markup under thesrc/templates/<template>/asset/pages folder.

FIG. 18 is a flowchart of a method for providing a user interface fordynamic site compilation in a cloud-based content hub environment, inaccordance with an embodiment.

In accordance with an embodiment, at step 1810, the method can provideat a computer including a microprocessor; a cloud-based content hub, thecloud based-content hub comprising an application interface adapted toreceive commands, a content management system comprising at least onedatabase, a website development kit having a connection to at least thecontent management system and a user interface, and a web servercomprising a website database.

In accordance with an embodiment, at step 1820, the method can provide acontent analytics engine, the content analytics engine being associatedwith a cache comprising a training set.

In accordance with an embodiment, at step 1830, the method can displayvia a graphical user interface of the user interface, representations ofa plurality of content items, each of the content items being stored atthe content management system.

In accordance with an embodiment, at step 1840, the method can perform,by the content analytics engine, an optimization analysis of a contentitem of the plurality of content items.

In accordance with an embodiment, at step 1850, the method can display aresult of the optimization analysis of the content item of the pluralityof content items via the graphical user interface.

FIG. 19 is a flowchart of a method for providing custom componentcompilation within a cloud-based content hub environment, in accordancewith an embodiment.

In accordance with an embodiment, at step 1910, the method can provide,at a computer including a microprocessor, a cloud-based content hubcomprising an application interface adapted to receive commands, acontent management system comprising at least one database, a websitedevelopment kit having a connection to at least the content managementsystem and a user interface, a web server comprising a website database,and a compiler, the compiler having access to a repository of compilerinstructions.

In accordance with an embodiment, at step 1920, the method can receivean instruction to compile a website, the instruction including at leastone content item at the content management database.

In accordance with an embodiment, at step 1930, the method can check aninstance of the content item for metadata indicative of an indication tocompile the content item statically or dynamically.

In accordance with an embodiment, at step 1940, the method can, upon themetadata being indicative to compile the instance of the content itemstatically, and upon a compiler instruction being present in therepository, the compiler instruction being associated with a type of thecontent item, compile the instance of the content item statically.

FIG. 20 is a flowchart of a method for automatic selection for dynamicsite compilation in a cloud-based content hub environment, in accordancewith an embodiment.

In accordance with an embodiment, at step 2010, the method can provide,at a computer including a microprocessor, a cloud-based content hubcomprising an application interface adapted to receive commands, acontent management system comprising at least one database, a websitedevelopment kit having a connection to at least the content managementsystem, and a web server comprising a website database.

In accordance with an embodiment, at step 2020, the method can provide acontent analytics engine, the content analytics engine being associatedwith a cache comprising a training set.

In accordance with an embodiment, at step 2030, the method can receivecommands, via the application interface, to build a website, wherein thecommands target at least one content item stored at the contentmanagement system.

In accordance with an embodiment, at step 2040, the method can associatethe at least one content item, after being targeted by the commands,with at least one metadata tag.

In accordance with an embodiment, at step 2050, the method can perform,by the content analytics engine, an optimization analysis of the atleast one content item associated with the metadata tag.

In accordance with an embodiment, at step 2060, the method canautomatically set the metadata tag based upon a result of theoptimization analysis.

In accordance with an embodiment, at step 2070, the method can compileand publish, by the website development kit, a website based at leastupon the received commands, the compiled website comprising the at leastone content item, the compiled website being publicly accessible.

FIG. 21 is a flowchart of a method for automatic suggestion for dynamicsite compilation in a cloud-based content hub environment, in accordancewith an embodiment.

In accordance with an embodiment, at step 2110, the method can provide,at a computer including a microprocessor, a cloud-based content hubcomprising an application interface adapted to receive commands, acontent management system comprising at least one database, a websitedevelopment kit having a connection to at least the content managementsystem, and a web server comprising a website database.

In accordance with an embodiment, at step 2120, the method can provide acontent analytics engine, the content analytics engine being associatedwith a cache comprising a training set.

In accordance with an embodiment, at step 2130, the method can receivecommands, via the application interface, to build a website, wherein thecommands target at least one content item stored at the contentmanagement system.

In accordance with an embodiment, at step 2140, the method can associatethe at least one content item, after being targeted by the commands,with at least one metadata tag.

In accordance with an embodiment, at step 2150, the method can perform,by the content analytics engine, an optimization analysis of the atleast one content item associated with the metadata tag.

In accordance with an embodiment, at step 2160, the method can, basedupon a result of the optimization analysis, automatically generate asuggestion regarding a setting of the metadata tag.

In accordance with an embodiment, at step 2170, the method can compileand publish, by the website development kit, a website based at leastupon the received commands, the compiled website comprising the at leastone content item, the compiled website being publicly accessible

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexample, and not limitation. The embodiments were chosen and describedin order to explain the features and principles of the invention and itspractical application. The embodiments illustrate systems and methods inwhich the various features of the present invention are utilized toimprove the performance of the systems and methods by providing newand/or improved functions, and/or providing performance advantagesincluding, but not limited to, reduced resource utilization, increasedcapacity, increased throughput, improved efficiency, reduced latency,enhanced security, and/or improved ease of use.

Some embodiments of the present invention are described herein withreference to flowcharts and/or block diagrams of methods, apparatus(systems), and computer program products which illustrate thearchitecture, functionality, process, and/or operation. Each block inthe flowchart or block diagram represents an element, function, process,module, segment, or portion of instructions, which comprises one or moreexecutable instructions for implementing the specified function. In somealternative embodiments, the functions noted in a block diagram orflowchart, occur out of the order noted in the figures. For example, twoblocks shown in succession may be executed substantially concurrently,or in the reverse order, depending upon the functionality involved. Eachblock of the flowcharts and/or block diagrams, and combinations ofblocks in the flowcharts and/or block diagrams, can be implemented bycomputer program instructions, and/or by special purpose hardware,and/or combinations of hardware and computer program instructions, whichperform the specified functions.

In some embodiments, features of the present invention are implementedin a computer including a processor, a computer-readable storage medium,and a network card/interface for communicating with other computers. Insome embodiments, features of the present invention are implemented in anetwork computing environment comprising a computing system includingvarious types of computer configurations, including personal computers,hand-held devices, multi-processor systems, microprocessor-based orprogrammable consumer electronics, network PCs, minicomputers, mainframecomputers, and the like interconnected by a network. The network can bea Local Area Network (LAN), switch fabric network (e.g. InfiniBand),Wide Area Network (WAN), and/or the Internet. The network can includecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers.

In some embodiments, features of the present invention are implementedin a computing system that includes a back-end component (e.g., as adata server), or that includes a middleware component (e.g., anapplication server), or that includes a front-end component (e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an implementation of the subjectmatter described herein), or any combination of such back-end,middleware, or front-end components interconnected by a network. Thecomputing system can include clients and servers having a client-serverrelationship to each other. In some embodiments, features of theinvention are implemented in a computing system comprising a distributedcomputing environment in which one or more clusters of computers areconnected by a network. The distributed computing environment can haveall computers at a single location or have clusters of computers atdifferent remote geographic locations connected by a network.

In some embodiments, features of the present invention are implementedin the cloud as part of, or as a service of, a cloud computing systembased on shared, elastic resources delivered to users in a self-service,metered manner using Web technologies. Characteristics of the cloud mayinclude, for example: on-demand self-service; broad network access;resource pooling; rapid elasticity; and measured service. Clouddeployment models include: Public, Private, and Hybrid. Cloud servicemodels include Software as a Service (SaaS), Platform as a Service(PaaS), Database as a Service (DBaaS), and Infrastructure as a Service(IaaS). The cloud generally refers to the combination of hardware,software, network, and web technologies which delivers shared elasticresources to users. The cloud, as used herein, may include public cloud,private cloud, and/or hybrid cloud embodiments, and may include cloudSaaS, cloud DBaaS, cloud PaaS, and/or cloud IaaS deployment models.

In some embodiments, features of the present invention are implementedusing, or with the assistance of hardware, software, firmware, orcombinations thereof. In some embodiments, features of the presentinvention are implemented using a processor configured or programmed toexecute one or more functions of the present invention. The processor isin some embodiments a single or multi-chip processor, a digital signalprocessor (DSP), a system on a chip (SOC), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic device, state machine, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. In someimplementations, features of the present invention are implemented bycircuitry that is specific to a given function. In otherimplementations, features are implemented in a computer, computingsystem, processor, and/or network, configured to perform particularfunctions using instructions stored e.g. on a computer-readable storagemedia.

In some embodiments, features of the present invention are incorporatedin software and/or firmware for controlling the hardware of a processingand/or networking system, and for enabling a processor and/or network tointeract with other systems utilizing the features of the presentinvention. Such software or firmware may include, but is not limited to,application program code, device drivers, operating systems, virtualmachines, hypervisors, application programming interfaces, programminglanguages, and execution environments/containers. Appropriate softwarecoding can readily be prepared by skilled programmers based on theteachings of the present disclosure.

In some embodiments, the present invention includes a computer programproduct which is a machine-readable or computer-readable storage medium(media) having instructions comprising software and/or firmware storedthereon/in, which instructions can be used to program or otherwiseconfigure a system such as a computer to perform any of the processes orfunctions of the present invention. The storage medium or computerreadable medium can include any type of media or device suitable forstoring instructions and/or data including, but not limited to, floppydisks, hard drives, solid state drives, optical discs, DVD, CD-ROMs,microdrives, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs,DRAMs, VRAMs, flash memory devices, magnetic or optical cards, molecularmemories, nanosystems, or variations and combinations thereof. Inparticular embodiments, the storage medium or computer readable mediumis a non-transitory machine-readable storage medium or non-transitorycomputer-readable storage medium.

The foregoing description is not intended to be exhaustive or to limitthe invention to the precise forms disclosed. Additionally, whereembodiments of the present invention have been described using aparticular series of transactions and steps, it should be apparent tothose skilled in the art that, unless stated, the embodiment does notexclude performance of additional transactions and steps. Further, whilethe various embodiments describe particular combinations of features ofthe invention it should be understood that different combinations of thefeatures will be apparent to persons skilled in the relevant art aswithin the scope of the invention. In particular, a feature (device-likeor method-like) recited in a given embodiment, variant, or shown in adrawing may be combined with or replace another feature in anotherembodiment, variant or drawing, without departing from the scope of thepresent invention. Moreover, it will be apparent to persons skilled inthe relevant art that various additions, subtractions, deletions,variations, substitutions of elements with equivalents, and othermodifications and changes in form, detail, implementation andapplication can be made therein without departing from the spirit andscope of the invention. It is intended that the broader spirit and scopeof the invention be defined by the following claims and theirequivalents.

What is claimed is:
 1. A system for providing custom component compilation within a cloud-based content hub environment, comprising: a computer including a microprocessor; a cloud-based content hub comprising an application interface adapted to receive commands, a content management system comprising at least one database, a website development kit having a connection to at least the content management system and a user interface, a web server comprising a website database, and a compiler, the compiler having access to a repository of compiler instructions; wherein an instruction to compile a website is received, the instruction including at least one content item at the content management database; wherein an instance of the content item is checked for metadata indicative of an indication to compile the content item statically or dynamically; and wherein upon the metadata being indicative to compile the instance of the content item statically, and upon a compiler instruction being present in the repository, the compiler instruction being associated with a type of the content item, the instance of the content item is compiled statically.
 2. The system of claim 1, wherein upon the metadata being indicative to compile the instance of the content item dynamically, the instance of the content item is rendered at runtime of the website.
 3. The system of claim 2, wherein upon the metadata being indicative to compile the instance of the content item statically, and upon the compiler instruction not being present in the repository, the compiler instruction being associated with a type of the content item, the instance of the content item is rendered at runtime of the website.
 4. The system of claim 3, wherein the instruction to compile the website is received via the user interface, the instruction comprising the metadata indicative of the indication to compile the instance of the content item statically or dynamically.
 5. The system of claim 3, further comprising: a content analytics engine, the content analytics engine being associated with a cache comprising a training set.
 6. The system of claim 5, wherein the instruction to compile the website is received via content analytics engine, the instruction comprising the metadata indicative of the indication to compile the instance of the content item statically or dynamically.
 7. The system of claim 6, wherein the instruction comprising the metadata is a result of an optimization analysis of the content item performed by the content analytics engine, the optimization analysis being based upon content analytics and consumption analytics of the content item.
 8. A method for providing custom component compilation within a cloud-based content hub environment, comprising: providing, at a computer including a microprocessor, a cloud-based content hub comprising an application interface adapted to receive commands, a content management system comprising at least one database, a website development kit having a connection to at least the content management system and a user interface, a web server comprising a website database, and a compiler, the compiler having access to a repository of compiler instructions; receiving an instruction to compile a website, the instruction including at least one content item at the content management database; checking an instance of the content item for metadata indicative of an indication to compile the content item statically or dynamically; and upon the metadata being indicative to compile the instance of the content item statically, and upon a compiler instruction being present in the repository, the compiler instruction being associated with a type of the content item, compiling the instance of the content item statically.
 9. The system of claim 8, wherein upon the metadata being indicative to compile the instance of the content item dynamically, the content item is rendered at runtime of the website.
 10. The system of claim 9, wherein upon the metadata being indicative to compile the instance of the content item statically, and upon the compiler instruction not being present in the repository, the compiler instruction being associated with a type of the content item, the instance of the content item is rendered at runtime of the website.
 11. The system of claim 10, wherein the instruction to compile the website is received via the user interface, the instruction comprising the metadata indicative of the indication to compile the instance of the content item statically or dynamically.
 12. The system of claim 10, further comprising: providing a content analytics engine, the content analytics engine being associated with a cache comprising a training set.
 13. The system of claim 12, wherein the instruction to compile the website is received via content analytics engine, the instruction comprising the metadata indicative of the indication to compile the instance of the content item statically or dynamically.
 14. The system of claim 13, wherein the instruction comprising the metadata is a result of an optimization analysis of the instance of the content item performed by the content analytics engine, the optimization analysis being based upon content analytics and consumption analytics of the instance of the content item.
 15. A non-transitory computer readable storage medium having instructions thereon for providing custom component compilation within a cloud-based content hub environment, which when read and executed by a computer cause the computer to perform steps comprising: providing, at a computer including a microprocessor, a cloud-based content hub comprising an application interface adapted to receive commands, a content management system comprising at least one database, a website development kit having a connection to at least the content management system and a user interface, a web server comprising a website database, and a compiler, the compiler having access to a repository of compiler instructions; receiving an instruction to compile a website, the instruction including at least one content item at the content management database; checking an instance of the content item for metadata indicative of an indication to compile the content item statically or dynamically; and upon the metadata being indicative to compile the instance of the content item statically, and upon a compiler instruction being present in the repository, the compiler instruction being associated with a type of the content item, compiling the instance of the content item statically.
 16. The non-transitory computer readable storage medium of claim 15, wherein upon the metadata being indicative to compile the instance of the content item dynamically, the content item is rendered at runtime of the website.
 17. The non-transitory computer readable storage medium of claim 16, wherein upon the metadata being indicative to compile the instance of the content item statically, and upon the compiler instruction not being present in the repository, the compiler instruction being associated with a type of the content item, the instance of the content item is rendered at runtime of the website.
 18. The non-transitory computer readable storage medium of claim 17, wherein the instruction to compile the website is received via the user interface, the instruction comprising the metadata indicative of the indication to compile the instance of the content item statically or dynamically.
 19. The non-transitory computer readable storage medium of claim 17, the steps further comprising: providing a content analytics engine, the content analytics engine being associated with a cache comprising a training set.
 20. The non-transitory computer readable storage medium of claim 19, wherein the instruction to compile the website is received via content analytics engine, the instruction comprising the metadata indicative of the indication to compile the instance of the content item statically or dynamically; and wherein the instruction comprising the metadata is a result of an optimization analysis of the instance of the content item performed by the content analytics engine, the optimization analysis being based upon content analytics and consumption analytics of the instance of the content item. 